Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ssingudasu/bug fix conn timeout flag #203

Merged
merged 2 commits into from
Jun 14, 2024

Conversation

ssingudasu
Copy link
Contributor

Description:

This PR is a bug fix to honor kafka --conn-timeout flag when --cluster-config is provided

@ssingudasu ssingudasu requested a review from a team as a code owner June 13, 2024 20:52
@ssingudasu ssingudasu merged commit 17d49c2 into master Jun 14, 2024
8 checks passed
@ssingudasu ssingudasu deleted the ssingudasu/bug-fix-conn-timeout-flag branch June 14, 2024 15:17
@rudo-ro
Copy link

rudo-ro commented Jul 8, 2024

hi @ssingudasu curious if you had any ideas here?

worker-0-1  |         time="2024-07-08 03:35:46" level=info msg="Creating new topic with config {Topic:topic_name NumPartitions:6 ReplicationFactor:1 ReplicaAssignments:[] ConfigEntries:[{ConfigName:retention.ms ConfigValue:259200000}]}"
worker-0-1  |         time="2024-07-08 03:35:48" level=error msg="map[topic_name:[7] Request Timed Out: the request exceeded the user-specified time limit in the request]"

seen on both 1.16.1 and 1.18.0 - is this a flag that can be set manually on topicctl? I don't see it documented.

using a sasl with --cluster-config file if that's helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants